I'm now reasonably confident in this as a first revision for WSON, and it can reuse the same flex PCB as SOIC8-Wide. It's possible the interposer block will need some tweaking later on, but I think this can be merged now.

@DodoidOfficial nice progress!!!

As when https://github.com/linuxboot/flashkeeper/pull/14/files was done, I would expect a png dropped under images/ and referred by docs/index.md to be rendered by github publish on website.

Any reason why this is not a branch in your repo rendering under GitHub pages so that changes in docs could be reviewed per https://dodoidofficial.github.io/flashkeeper/ as my fork can be seen per https://tlaurion.github.io/flashkeeper/ ?

Pointing your fork github page to your fork's branch will make it rendered for PR review in the future, not requiring other to validate changes prior of PR merge ourside of code/changes review, so that others can follow same process later for Docs related PR.

Fork this repo/sync it with linuxboot/flashkeeker (my default branch is test here)

This would be done like this under your fork's settings (same test branch):

In your case, it would be wson branch here. If you do this prior of next commit, the webpage will be rendered automatically from that branch over https://dodoidofficial.github.io/flashkeeper/ for you/me/anyone to review prior of merge.

Thanks! I will add an image showing the interposer to the documentation.

I generally review documentation changes using Jekyll's local preview/development server (jekyll serve --config docs/_config-local.yml --host 0.0.0.0) - GitHub Pages just serves the "production" version. This works pretty well, and it's convenient while writing (versus committing just to preview changes).

LGTM per code review alone! Merging!